home *** CD-ROM | disk | FTP | other *** search
-
-
-
- iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV iiiinnnnffffooooccccmmmmpppp((((1111MMMM))))
-
-
-
- NNNNAAAAMMMMEEEE
- iiiinnnnffffooooccccmmmmpppp - compare or print out _t_e_r_m_i_n_f_o descriptions
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- iiiinnnnffffooooccccmmmmpppp [----ddddccccnnnnppppIIIILLLLCCCCuuuuVVVV1111] [----vvvv _n] [----ssss dddd| iiii| llll| cccc]
- [----wwww _w_i_d_t_h] [----AAAA _d_i_r_e_c_t_o_r_y] [----BBBB _d_i_r_e_c_t_o_r_y] [_t_e_r_m_n_a_m_e...]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- iiiinnnnffffooooccccmmmmpppp can be used to compare a binary tttteeeerrrrmmmmiiiinnnnffffoooo entry with
- other terminfo entries, rewrite a tttteeeerrrrmmmmiiiinnnnffffoooo description to
- take advantage of the uuuusssseeee==== terminfo field, or print out a
- tttteeeerrrrmmmmiiiinnnnffffoooo description from the binary file (tttteeeerrrrmmmm) in a
- variety of formats. In all cases, the boolean fields will
- be printed first, followed by the numeric fields, followed
- by the string fields.
-
-
- DDDDeeeeffffaaaauuuulllltttt OOOOppppttttiiiioooonnnnssss
- If no options are specified and zero or one _t_e_r_m_n_a_m_e_s are
- specified, the ----IIII option will be assumed. If more than one
- _t_e_r_m_n_a_m_e is specified, the ----dddd option will be assumed.
-
-
- CCCCoooommmmppppaaaarrrriiiissssoooonnnn OOOOppppttttiiiioooonnnnssss [[[[----dddd]]]] [[[[----cccc]]]] [[[[----nnnn]]]]
- iiiinnnnffffooooccccmmmmpppp compares the tttteeeerrrrmmmmiiiinnnnffffoooo description of the first
- terminal _t_e_r_m_n_a_m_e with each of the descriptions given by the
- entries for the other terminal's _t_e_r_m_n_a_m_e_s. If a capability
- is defined for only one of the terminals, the value returned
- will depend on the type of the capability: FFFF for boolean
- variables, ----1111 for integer variables, and NNNNUUUULLLLLLLL for string
- variables.
-
- The ----dddd option produces a list of each capability that is
- different between two entries. This option is useful to
- show the difference between two entries, created by
- different people, for the same or similar terminals.
-
- The ----cccc option produces a list of each capability that is
- common between two entries. Capabilities that are not set
- are ignored. This option can be used as a quick check to
- see if the ----uuuu option is worth using.
-
- The ----nnnn option produces a list of each capability that is in
- neither entry. If no _t_e_r_m_n_a_m_e_s are given, the environment
- variable TTTTEEEERRRRMMMM will be used for both of the _t_e_r_m_n_a_m_e_s. This
- can be used as a quick check to see if anything was left out
- of a description.
-
-
- SSSSoooouuuurrrrcccceeee LLLLiiiissssttttiiiinnnngggg OOOOppppttttiiiioooonnnnssss [[[[----IIII]]]] [[[[----LLLL]]]] [[[[----CCCC]]]]
- The ----IIII, ----LLLL, and ----CCCC options will produce a source listing for
- each terminal named.
-
-
-
- Page 1 (printed 5/12/99)
-
-
-
-
-
-
- iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV iiiinnnnffffooooccccmmmmpppp((((1111MMMM))))
-
-
-
- ----IIII use the tttteeeerrrrmmmmiiiinnnnffffoooo names
- ----LLLL use the long C variable name listed in <tttteeeerrrrmmmm....hhhh>
- ----CCCC use the tttteeeerrrrmmmmccccaaaapppp names
- ----rrrr when using ----CCCC, put out all capabilities in tttteeeerrrrmmmmccccaaaapppp form
-
- If no _t_e_r_m_n_a_m_e_s are given, the environment variable TTTTEEEERRRRMMMM
- will be used for the terminal name.
-
- The source produced by the ----CCCC option may be used directly as
- a tttteeeerrrrmmmmccccaaaapppp entry, but not all parameterized strings can be
- changed to the tttteeeerrrrmmmmccccaaaapppp format. iiiinnnnffffooooccccmmmmpppp will attempt to
- convert most of the parameterized information, and anything
- not converted will be plainly marked in the output and
- commented out. These should be edited by hand.
-
- All padding information for strings will be collected
- together and placed at the beginning of the string where
- tttteeeerrrrmmmmccccaaaapppp expects it. Mandatory padding (padding information
- with a trailing '/') will become optional.
-
- All tttteeeerrrrmmmmccccaaaapppp variables no longer supported by tttteeeerrrrmmmmiiiinnnnffffoooo, but
- which are derivable from other tttteeeerrrrmmmmiiiinnnnffffoooo variables, will be
- output. Not all tttteeeerrrrmmmmiiiinnnnffffoooo capabilities will be translated;
- only those variables which were part of tttteeeerrrrmmmmccccaaaapppp will
- normally be output. Specifying the ----rrrr option will take off
- this restriction, allowing all capabilities to be output in
- _t_e_r_m_c_a_p form.
-
- Note that because padding is collected to the beginning of
- the capability, not all capabilities are output. Mandatory
- padding is not supported. Because tttteeeerrrrmmmmccccaaaapppp strings are not
- as flexible, it is not always possible to convert a tttteeeerrrrmmmmiiiinnnnffffoooo
- string capability into an equivalent tttteeeerrrrmmmmccccaaaapppp format. A
- subsequent conversion of the tttteeeerrrrmmmmccccaaaapppp file back into tttteeeerrrrmmmmiiiinnnnffffoooo
- format will not necessarily reproduce the original tttteeeerrrrmmmmiiiinnnnffffoooo
- source.
-
- Some common tttteeeerrrrmmmmiiiinnnnffffoooo parameter sequences, their tttteeeerrrrmmmmccccaaaapppp
- equivalents, and some terminal types which commonly have
- such sequences, are:
-
- tttteeeerrrrmmmmiiiinnnnffffoooo tttteeeerrrrmmmmccccaaaapppp Representative Terminals
- ____________________________________________________________________________________________________________________________
- %%%%pppp1111%%%%cccc %%%%.... adm
- %%%%pppp1111%%%%dddd %%%%dddd hp, ANSI standard, vt100
- %%%%pppp1111%%%%''''xxxx''''%%%%++++%%%%cccc %%%%++++xxxx concept
- %%%%iiii %%%%iiiiq ANSI standard, vt100
- %%%%pppp1111%%%%????%%%%''''xxxx''''%%%%>>>>%%%%tttt%%%%pppp1111%%%%''''yyyy''''%%%%++++%%%%;;;; %%%%>>>>xxxxyyyy concept
- %%%%pppp2222 is printed before %%%%pppp1111 %%%%rrrr hp
-
- UUUUsssseeee==== OOOOppppttttiiiioooonnnn [[[[----uuuu]]]]
- The ----uuuu option produces a tttteeeerrrrmmmmiiiinnnnffffoooo source description of the
- first terminal _t_e_r_m_n_a_m_e which is relative to the sum of the
-
-
- Page 2 (printed 5/12/99)
-
-
-
-
-
-
- iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV iiiinnnnffffooooccccmmmmpppp((((1111MMMM))))
-
-
-
- descriptions given by the entries for the other terminals
- _t_e_r_m_n_a_m_e_s. It does this by analyzing the differences
- between the first _t_e_r_m_n_a_m_e and the other _t_e_r_m_n_a_m_e_s and
- producing a description with uuuusssseeee==== fields for the other
- terminals. In this manner, it is possible to retrofit
- generic terminfo entries into a terminal's description. Or,
- if two similar terminals exist, but were coded at different
- times or by different people so that each description is a
- full description, using iiiinnnnffffooooccccmmmmpppp will show what can be done
- to change one description to be relative to the other.
-
- A capability will get printed with an at-sign (@) if it no
- longer exists in the first _t_e_r_m_n_a_m_e, but one of the other
- _t_e_r_m_n_a_m_e entries contains a value for it. A capability's
- value gets printed if the value in the first _t_e_r_m_n_a_m_e is not
- found in any of the other _t_e_r_m_n_a_m_e entries, or if the first
- of the other _t_e_r_m_n_a_m_e entries that has this capability gives
- a different value for the capability than that in the first
- _t_e_r_m_n_a_m_e.
-
- The order of the other _t_e_r_m_n_a_m_e entries is significant.
- Since the terminfo compiler ttttiiiicccc does a left-to-right scan of
- the capabilities, specifying two uuuusssseeee==== entries that contain
- differing entries for the same capabilities will produce
- different results depending on the order that the entries
- are given in. iiiinnnnffffooooccccmmmmpppp will flag any such inconsistencies
- between the other _t_e_r_m_n_a_m_e entries as they are found.
-
- Alternatively, specifying a capability _a_f_t_e_r a uuuusssseeee==== entry
- that contains that capability will cause the second
- specification to be ignored. Using iiiinnnnffffooooccccmmmmpppp to recreate a
- description can be a useful check to make sure that
- everything was specified correctly in the original source
- description.
-
- Another error that does not cause incorrect compiled files,
- but will slow down the compilation time, is specifying extra
- uuuusssseeee==== fields that are superfluous. iiiinnnnffffooooccccmmmmpppp will flag any
- other _t_e_r_m_n_a_m_e _u_s_e= fields that were not needed.
-
-
- OOOOtttthhhheeeerrrr OOOOppppttttiiiioooonnnnssss [[[[----ssss dddd||||iiii||||llll||||cccc]]]] [[[[----vvvv]]]] [[[[----VVVV]]]]
- The ----ssss option sorts the fields within each type according to
- the argument below:
-
-
- dddd leave fields in the order that they are stored in the
- _t_e_r_m_i_n_f_o database.
-
- iiii sort by _t_e_r_m_i_n_f_o name.
-
- llll sort by the long C variable name.
-
-
-
- Page 3 (printed 5/12/99)
-
-
-
-
-
-
- iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV iiiinnnnffffooooccccmmmmpppp((((1111MMMM))))
-
-
-
- cccc sort by the _t_e_r_m_c_a_p name.
-
- If the ----ssss option is not given, the fields printed out
- will be sorted alphabetically by the tttteeeerrrrmmmmiiiinnnnffffoooo name
- within each type, except in the case of the ----CCCC or the
- ----LLLL options, which cause the sorting to be done by the
- tttteeeerrrrmmmmccccaaaapppp name or the long C variable name, respectively.
-
-
- ----FFFF compare terminfo files. This assumes that two
- following arguments are filenames. The files are
- searched for pairwise matches between entries, with two
- entries considered to match if any of their names do.
- The report printed to standard output lists entries
- with no matches in the other file, and entries with
- more than one match. For entries with exactly one
- match it includes a difference report.
-
- ----pppp Ignore padding specifications when comparing strings.
-
- ----vvvv _n prints out tracing information on standard error as the
- program runs. Higher values of n induce greater
- verbosity.
-
- ----VVVV prints out the version of the program in use on
- standard error and exits.
-
- ----1111 causes the fields to be printed out one to a line.
- Otherwise, the fields will be printed several to a line
- to a maximum width of 60 characters.
-
- ----TTTT eliminates size-restrictions on the generated text.
- This is mainly useful for testing and analysis, since
- the compiled descriptions are limited (e.g., 1023 for
- termcap, 4096 for terminfo).
-
- ----wwww changes the output to _w_i_d_t_h characters.
-
- ----RRRR_s_u_b_s_e_t
- Restrict output to a given subset. This option is for
- use with archaic versions of terminfo like those on
- SVr1, Ultrix, or HP/UX that don't support the full set
- of SVR4/XSI Curses terminfo; and outright broken ports
- like AIX that have their own extensions incompatible
- with SVr4/XSI. Available terminfo subsets are "SVr1",
- "Ultrix", "HP", and "AIX"; see tttteeeerrrrmmmmiiiinnnnffffoooo(5) for details.
- You can also choose the subset "BSD" which selects only
- capabilities with termcap equivalents recognized by
- 4.4BSD.
-
- ----eeee Dump the capabilities of the given terminal as a C
- initializer for a TERMTYPE structure (the terminal
-
-
-
- Page 4 (printed 5/12/99)
-
-
-
-
-
-
- iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV iiiinnnnffffooooccccmmmmpppp((((1111MMMM))))
-
-
-
- capability structure in the <<<<tttteeeerrrrmmmm....hhhh>>>>). This option is
- useful for preparing versions of the curses library
- hardwired for a given terminal type.
-
- CCCChhhhaaaannnnggggiiiinnnngggg DDDDaaaattttaaaabbbbaaaasssseeeessss [[[[----AAAA _d_i_r_e_c_t_o_r_y]]]] [[[[----BBBB _d_i_r_e_c_t_o_r_y]]]]
- The location of the compiled tttteeeerrrrmmmmiiiinnnnffffoooo database is taken from
- the environment variable TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO . If the variable is not
- defined, or the terminal is not found in that location, the
- system tttteeeerrrrmmmmiiiinnnnffffoooo database, in @@@@DDDDAAAATTTTAAAADDDDIIIIRRRR@@@@////tttteeeerrrrmmmmiiiinnnnffffoooo, will be
- used. The options ----AAAA and ----BBBB may be used to override this
- location. The ----AAAA option will set TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO for the first
- _t_e_r_m_n_a_m_e and the ----BBBB option will set TTTTEEEERRRRMMMMIIIINNNNFFFFOOOO for the other
- _t_e_r_m_n_a_m_e_s. With this, it is possible to compare
- descriptions for a terminal with the same name located in
- two different databases. This is useful for comparing
- descriptions for the same terminal created by different
- people.
-
- ----iiii Analyze the initialization (iiiissss1111, iiiissss2222, iiiissss3333), and reset
- (rrrrssss1111, rrrrssss2222, rrrrssss3333), strings in the entry. For each
- string, the code tries to analyze it into actions in
- terms of the other capabilities in the entry, certain
- X3.64/ISO 6429/ECMA-48 capabilities, and certain DEC
- VT-series private modes (the set of recognized special
- sequences has been selected for completeness over the
- existing terminfo database). Each report line consists
- of the capability name, followed by a colon and space,
- followed by a printable expansion of the capability
- string with sections matching recognized actions
- translated into {}-bracketed descriptions. Here is a
- list of the DEC/ANSI special sequences recognized:
-
- Action Meaning
- ________________________________________________________________________________
- RIS full reset
- SC save cursor
- RC restore cursor
- LL home-down
- RSR reset scroll region
-
- ISO DEC G0 enable DEC graphics for G0
- ISO UK G0 enable UK chars for G0
- ISO US G0 enable US chars for G0
- ISO DEC G1 enable DEC graphics for G1
- ISO UK G1 enable UK chars for G1
- ISO US G1 enable US chars for G1
-
- DECPAM application keypad mode
- DECPNM normal keypad mode
- DECANSI enter ANSI mode
-
-
-
-
-
- Page 5 (printed 5/12/99)
-
-
-
-
-
-
- iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV iiiinnnnffffooooccccmmmmpppp((((1111MMMM))))
-
-
-
- DEC[+-]CKM application cursor keys
- DEC[+-]ANM set VT52 mode
- DEC[+-]COLM 132-column mode
- DEC[+-]SCLM smooth scroll
- DEC[+-]SCNM reverse video mode
- DEC[+-]OM origin mode
- DEC[+-]AWM wraparound mode
- DEC[+-]ARM auto-repeat mode
-
- It also recognizes a SGR action corresponding to
- ANSI/ISO 6429/ECMA Set Graphics Rendition, with the
- values NORMAL, BOLD, UNDERLINE, BLINK, and REVERSE.
- All but NORMAL may be prefixed with `+' (turn on) or
- `-' (turn off). An SGR0 designates an empty highlight
- sequence (equivalent to {SGR:NORMAL}).
-
- FFFFIIIILLLLEEEESSSS
- @DATADIR@/terminfo Compiled terminal description database.
-
- EEEEXXXXTTTTEEEENNNNSSSSIIIIOOOONNNNSSSS
- The ----FFFF option is not supported in SVr4 curses. (It is
- primarily intended to help infocmp's author, while wearing
- his terminfo/termcap maintainer hat, merge termcap/terminfo
- files from various sources into the master.)
-
- The ----RRRR, ----pppp, ----eeee, ----TTTT and ----iiii options are not supported in SVr4
- curses.
-
- The ----rrrr option's notion of `termcap' capabilities is System V
- Release 4's. Actual BSD curses versions will have a more
- restricted set. To see only the 4.4BSD set, use -r -RBSD.
-
- BBBBUUUUGGGGSSSS
- The -F option of iiiinnnnffffooooccccmmmmpppp(1M) should be a ttttooooeeee(1M) mode.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- iiiinnnnffffooooccccmmmmpppp(1M), ccccaaaappppttttooooiiiinnnnffffoooo(1M), iiiinnnnffffoooottttooooccccaaaapppp(1M), ttttiiiicccc(1M), ttttooooeeee(1M),
- ccccuuuurrrrsssseeeessss(3X), tttteeeerrrrmmmmiiiinnnnffffoooo(5).
-
- AAAAUUUUTTTTHHHHOOOORRRR
- Eric S. Raymond <esr@snark.thyrsus.com>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 6 (printed 5/12/99)
-
-
-
-